Transformation of UML Activity Diagram for Enhanced Reasoning

IT industry has adopted the unified modelling language activity diagram (UML-AD) as a de facto standard. UML AD facilitates modellers to graphically represent and document business processes to show the flow of activities and behaviour of a system. However, UML AD has many drawbacks such as lack of formal semantics i.e. ontology used for the constructs based on intuition, that vaguely describes processes and no provision for verifiability. Petri Net (PN) has been around for decades and used to model the workflow systems but PNs and its variants are too complex for business process modellers with no prior experience. A logical foundation is desirable to construct a business process with a precision that facilitates in transforming UML AD into a formal mechanism supported by verifiability capabilities for enhanced reasoning. Therefore, in this paper, we will provide a framework that will provide formal definitions for UML AD core terms and constructs used for modelling, and subsequently transform them to formal representation called point graph(PG). This will provide an insight into UML AD and will improve the overall functionality required from a modelling tool. A case study is conducted at King’s College Hospital trust’ to improve their patient flows of an accident and emergency (A&E) department

Identifying Suitable Representation Techniques for the Prioritization of Requirements and Their Interdependencies for Multiple Software Product Lines

Software requirements typically do not exist independently of each other, rather most requirements have some type of dependency on another requirement [4]. For companies developing software products, which depend on each other, in so-called multiple software product lines (SPLs), systematic requirements management, including consideration for prioritization and inter‐ dependencies, is a time-consuming and convoluted task. Representation techniques for complex requirements can convey critical requirements interdependency information to make prioritization of requirements quicker and more accurate [1]. Based on reviewing the foremost literature, this paper identifies the representation techniques for requirements management which are most suitable for multiple software product lines (SPLs

Effect of alirocumab on mortality after acute coronary syndromes. An analysis of the ODYSSEY OUTCOMES randomized clinical trial

Background: Previous trials of PCSK9 (proprotein convertase subtilisin-kexin type 9) inhibitors demonstrated reductions in major adverse cardiovascular events, but not death. We assessed the effects of alirocumab on death after index acute coronary syndrome. Methods: ODYSSEY OUTCOMES (Evaluation of Cardiovascular Outcomes After an Acute Coronary Syndrome During Treatment With Alirocumab) was a double-blind, randomized comparison of alirocumab or placebo in 18 924 patients who had an ACS 1 to 12 months previously and elevated atherogenic lipoproteins despite intensive statin therapy. Alirocumab dose was blindly titrated to target achieved low-density lipoprotein cholesterol (LDL-C) between 25 and 50 mg/dL. We examined the effects of treatment on all-cause death and its components, cardiovascular and noncardiovascular death, with log-rank testing. Joint semiparametric models tested associations between nonfatal cardiovascular events and cardiovascular or noncardiovascular death. Results: Median follow-up was 2.8 years. Death occurred in 334 (3.5%) and 392 (4.1%) patients, respectively, in the alirocumab and placebo groups (hazard ratio [HR], 0.85; 95% CI, 0.73 to 0.98; P=0.03, nominal P value). This resulted from nonsignificantly fewer cardiovascular (240 [2.5%] vs 271 [2.9%]; HR, 0.88; 95% CI, 0.74 to 1.05; P=0.15) and noncardiovascular (94 [1.0%] vs 121 [1.3%]; HR, 0.77; 95% CI, 0.59 to 1.01; P=0.06) deaths with alirocumab. In a prespecified analysis of 8242 patients eligible for ≥3 years follow-up, alirocumab reduced death (HR, 0.78; 95% CI, 0.65 to 0.94; P=0.01). Patients with nonfatal cardiovascular events were at increased risk for cardiovascular and noncardiovascular deaths (P<0.0001 for the associations). Alirocumab reduced total nonfatal cardiovascular events (P<0.001) and thereby may have attenuated the number of cardiovascular and noncardiovascular deaths. A post hoc analysis found that, compared to patients with lower LDL-C, patients with baseline LDL-C ≥100 mg/dL (2.59 mmol/L) had a greater absolute risk of death and a larger mortality benefit from alirocumab (HR, 0.71; 95% CI, 0.56 to 0.90; Pinteraction=0.007). In the alirocumab group, all-cause death declined wit h achieved LDL-C at 4 months of treatment, to a level of approximately 30 mg/dL (adjusted P=0.017 for linear trend). Conclusions: Alirocumab added to intensive statin therapy has the potential to reduce death after acute coronary syndrome, particularly if treatment is maintained for ≥3 years, if baseline LDL-C is ≥100 mg/dL, or if achieved LDL-C is low. Clinical Trial Registration: URL: https://www.clinicaltrials.gov. Unique identifier: NCT01663402

A Redesign Framework for Call Centers

An important shortcoming in the Business Process Redesign (BPR) literature is the lack of concrete guidance on how to improve an existing business process. Our earlier work has aimed at filling this gap by identifying a set of BPR best practices. This paper takes a further step by showing how a set of best practices can be used to derive a redesign framework for a specific domain, in this case for call centers. Such a framework identifies the various available design options and specifies the relevant performance characteristics. To evaluate concrete design configurations (i.e., coherent combinations of design choices) we use a formal modelling approach based on Petri nets and the simulation tool CPN-Tools. An industrial case study is used to gather relevant context data. We expect that this work helps researchers and practitioners to optimize the performance of actual call centers and to set up similar frameworks for other domains